fix(supervisor): reject MCP initialize batches - #3192
Conversation
Signed-off-by: Shiju <shiju@nvidia.com>
johntmyers
left a comment
There was a problem hiding this comment.
gator-agent
PR Review Status
This focused fail-closed change is project-valid under accepted issue #2174. The initial code review found no blocking issues: MCP batches containing initialize are rejected before policy evaluation, generic JSON-RPC batch behavior remains unchanged, and focused parser regressions cover both paths.
Blocking findings:
- No blocking findings remain
Carried findings:
- None
Non-blocking suggestions:
- None
Gator metadata
- Validation: Focused supervisor-network prerequisite for accepted issue #2174
- Docs: Not needed; this is internal protocol enforcement with no direct user-facing UX change
- Checks: Current branch, DCO, vouch, and Helm gates are green; required E2E dispatch is being reconciled
- E2E:
test:e2erequired for network-proxy policy enforcement - Head SHA:
ecacd8d211223caca29dcdc0c96908093e478533 - Base SHA:
d7cb6e456db0dab6742d29dfca32bf9056be94cf - Merge base SHA:
c93b2fa7da3a40a6dd6c077973cb13d2755f7e50 - Patch ID:
a98e7fb797d5a1086ad9a5382417dfe9738bd7be - Gator payload:
8 - Review mode:
initial - Previous reviewed SHA: none
- Review budget exhausted: no
- Maintainer decision required: no
- Next state:
gator:in-review
|
Label |
Monitoring CompleteMonitoring is complete because this PR has merged. Final status: Gator review found no blocking issues, the required I removed the active Gator metadata
|
Summary
Reject an MCP
initializerequest when it appears in a JSON-RPC batch. Initialization is a standalone bootstrap exchange, so allowing it in a batch would make later profile selection ambiguous before policy evaluation can authorize or forward any member.Related Issue
Related to #2174. This is one small fail-closed prerequisite and does not close the roadmap issue.
Changes
initializecalls before policy evaluation.initializemethod, unchanged.Testing
mise run pre-commitpassesChecklist